UI/UX Best Practices
Good UX
Requires less mental effort to use.
Less mistakes when using it.
Do more, with less (steps, clicks, etc.).
Intuitive: Easy to learn/use & familiar to user.
General UI/UX Guidelines
Embrace the KISS (Keep It Simple Stupid) approach.
Try to keep everything not more than three clicks away.
User should not wait more than 2 seconds for any response.
Main goals of good UX: Simple & elegant, clear & consistent.
Try to break long and complex procedures to short and clear steps.
Don’t leave users in The Dark: keep the user informed of what is happening. Use loading detailed indicators, tooltips and informative labeling.
Avoid using the words "click here" for a button. Buttons should always be descriptive text.
Use meaningful title bars to summarize callout content. Keep titles under 75 characters.
Error prevention – Even better than good error messages is a careful design which prevents a problem from occurring in the first place.
Recognition rather than recall – Minimize the user's memory load by making objects, actions, and options visible.
Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
Keep menus short – A shorter menu with distinct categories is easier for mobile visitors to navigate.
Minimize form errors with labeling and real-time validation - Use clearly visible labels to let users know what you need and validate for errors in real time to let them know if there’s a problem before they submit a form.
Design efficient forms – Minimize the number of fields in your forms, and auto-fill information wherever possible. Use clearly-labeled progress bars to help users get through multi-part forms.
Use confirmation dialogs – Help the user understand what’s going on.
Text
Text should be legible at a typical viewing distance without zooming.
Make sure there is sufficient contrast between the text color and the background. This will improve readability.
Don't let text overlap. Improve legibility by increasing line height or letter spacing.
Do not cram more into a space than what can fit comfortably.
Avoid using all caps. It is easiest to read text that is in the standard upper and lowercase format.
Labels inside input fields: give the user hints and guides of what is accepted (e.g. “6-12 characters that contains numbers”).
Choose a simple and common font: fancy fonts are not readable and make the user work hard to decrypt.
Define a set of up to 3 font sizes and stay consistent with them throughout the application.